Guardex now refreshes active-session heartbeats while Codex runs, keeps repo-root dirt separate from managed sandboxes, and shows touched-file conflict context directly under each live session. The extension stays a viewer: stop actions route back through gx, and the shipped workspace copy stays aligned with the template copy.

Constraint: The VS Code extension must stay read-only for git and session lifecycle state

Constraint: Source and template extension trees must remain mirrored

Rejected: Kill session pids directly from the extension | bypasses gx lifecycle control and diverges from the read-only viewer contract

Confidence: high

Scope-risk: moderate

Directive: Keep launcher heartbeat freshness and lifecycle actions routed through gx rather than extension-side mutation

Tested: node --test test/vscode-active-agents-session-state.test.js

Tested: openspec validate agent-codex-improve-active-agents-extension-runtime-2026-04-22-16-55 --type change --strict

Tested: openspec validate --specs

Tested: bash -n scripts/codex-agent.sh

Tested: bash -n templates/scripts/codex-agent.sh

Tested: node --check scripts/agent-session-state.js

Tested: node --check src/context.js

Tested: node --check src/hooks/index.js

Tested: node --check vscode/guardex-active-agents/extension.js

Tested: node --check vscode/guardex-active-agents/session-schema.js

Not-tested: Manual VS Code interaction against a live sandbox session